Migration

export const router and export const hydrate where merged into export const csr. These two options really belong together, setting one to true and the other to false resulted in unexpected/buggy behavior. To migrate, remove the old options and replace them with the new option.

// +layout.js
- export const router = false;
- export const hydrate = false;
+ export const csr = false;

The following permutations are possible:

• old: router = true / hydrate = true -> new: csr = true (this is the default, so you probably don't need to set this)
• old: router = false / hydrate = false -> new: csr = false (no JS is loaded on the client)
• old: router = false / hydrate = true -> new: csr = true + set data-sveltekit-reload if you want native navigations
• old: router = true / hydrate = false -> new: csr = true (this was a buggy setting)

PR description

closes #6436

TODO:

• update create-svelte templates
• docs
• noisy error if a page has hydrate or router exports

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0